Resolves #6755 (FR-2593)

Summary

Introduces FolderCreateModalV2, a rewrite of the VFolder creation modal on the V2 GraphQL createVfolderV2 mutation. The bigger structural change in this PR is moving caller-intent (user vs. admin context) from implicit role inference into explicit, declarative props, and replacing the open-ended hiddenFormItems escape hatch with a typed folderType preset.

User / admin separation

Previously the original FolderCreateModal decided whether to expose the project-folder option purely by reading the current user's role:

{(userRole === 'admin' || userRole === 'superadmin') && _.includes(allowedTypes, 'group') && ...}

This leaks admin UI when a superadmin user opens the same modal from a user-facing page (e.g. their personal Data page) — they would see project folder creation that doesn't belong in that context.

FolderCreateModalV2 flips this: the page declares its context, and the modal honors it.

allowCreateProjectFolder?: boolean (default false)

Caller-controlled flag indicating the modal is being opened from an admin context where project folder creation should be exposed.

• User-facing pages omit it → project option is never shown, even for superadmins.
• Admin pages opt in by passing allowCreateProjectFolder → project option becomes available.
• The user role check (admin/superadmin) is kept as defense-in-depth, so a non-admin who somehow lands on an admin context (route-level permission misconfig) still cannot see the option.

Effective condition for showing the project option:

allowCreateProjectFolder && isAdmin && allowedTypes.includes('group')

folderType?: 'model_project'

Replaces the prior pattern of initialValues={...} + hiddenFormItems=[...] for "create a folder of a fixed shape" call sites. When set:

• Pre-selects usage_mode='model', type='project', permission='ro', cloneable=true (cloneable remains user-editable).
• Disables the structural radio groups so the user can see they are locked but cannot change them.
• Suppresses the existing warning tooltips/icons on disabled options for a clean read-only appearance.
• Caller still controls name and host.

folderType is intentionally a single-value union for now — extend it (e.g. 'model_user') when the next preset is needed instead of adding more boolean flags.

Removal of hiddenFormItems

The previous hiddenFormItems: HiddenFormItemsType[] prop is removed. It was a leaky abstraction: callers had to know the modal's internal field names and individually opt out of each option. All real uses were really one of two intents — "this is an admin context" or "this is a model_project preset" — both now expressed declaratively.

Caller updates

Other callers (StartPage, VFolderNodeListPage, VFolderTable, VFolderSelect) only used initialValues and are unaffected.

V2 mutation

Folder creation now uses the createVfolderV2 mutation. The response is mapped back to the existing FolderCreationResponse shape so downstream code (notification, event dispatch, callers consuming result.id) is unchanged. The REST list_allowed_types call is retained as there is no V2 equivalent yet.

Checklist: (if applicable)

• Documentation
• Minimum required manager version — verify createVfolderV2 mutation availability
• Specific setting for review (eg., KB link, endpoint or how to setup)
• Minimum requirements to check during review
• Test case(s) to demonstrate the difference of before/after
  • User-facing page (e.g. user Data page): superadmin should not see the project type option.
  • Admin page (AdminVFolderNodeListPage): admin should see the project type option via the new Create Folder button.
  • Admin Model Card / Import Artifact: opening the create-folder dialog should show the form locked to model+project+ro, with cloneable still toggleable.